Conversation
bmiddha
changed the title
apostolisms
approved these changes
Aug 26, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Remove timeout for VS Code shell integration
Make activation event more specific
Details
We had reports where users of the Debug Certificate Manger VS Code extension kept running into shell integration timeouts. This can happen when the shell boot up.
Shell integration is activated after the config files are sourced. So if there is anything in the
.bashrcor.bash_profilethat takes a while then thebashshell integration will be delayed.We also had cases where the extension does not activate even when
.vscode/debug-certificate-manager.jsonExtension host logs:
Updated activation event to be more specific in the file pattern. Hopefully this will make the search faster and not timeout.
How it was tested
Tested by adding
sleep 10to.bashrcTested that the extension still activates with the new pattern